Why Use APIs
Use APIs when:- The service you need is not covered by an MCP server
- You want more flexibility or control over endpoints
- You need to connect internal or specialized services
Authorization matters: After you authorize an API, available actions match your scopes and role.
Official APIs
CREAO maintains a set of ready-to-use APIs (e.g. OpenAI, search services, email/SMS). These are pre-configured and require only a key or sign-in.Custom APIs (Pro)
Pro users can connect any OpenAPI by providing documentation.
Third-Party Services
CRMs, payment processors, analytics tools, SaaS platforms
Internal Services
Company microservices or private APIs
Legacy Systems
Older systems with API access
Specialized Tools
Niche or industry-specific platforms
Setup Process
1
Provide Documentation
Upload OpenAPI spec, Postman collection, or endpoint details.

2
Configure Auth
Add API keys or OAuth credentials. CREAO stores them securely.
It can also be authenticated through the header.


3
Test Connection
Verify basic functionality before going live.

4
Map to Your App
Link endpoints to data tables, pages, or Copilot commands.

Lifecycle & Security
Connection Management
- Add APIs during app build or to existing apps anytime
- View all active APIs in your integration dashboard
- Remove or refresh credentials when needed
Security
- OAuth2 or encrypted API key storage
- HTTPS/TLS for all traffic
- Scoped access by user role and granted permissions
- Audit trail of API actions
Monitoring
- Track API usage and error rates
- Alerts when tokens expire or limits are hit
- Automatic retries for temporary failures
Troubleshooting
Auth Errors
Auth Errors
Check if tokens expired, keys are valid, and permissions match.
Rate Limits
Rate Limits
Reduce request frequency, add queuing, or upgrade your plan.
Data Format Issues
Data Format Issues
Verify request and response match the API’s expected schema.
Prefer one-click connectors?
Explore MCP Servers for faster setup